HTTP Trigger Node
The HTTP Trigger node acts as the execution entry point for HTTP-triggered workflows. It captures incoming HTTP request data and maps the request Body, QueryString, and Headers to workflow variables. Use this node when workflows need to be invoked via external HTTP calls rather than chatbot interactions.
How It Works
The HTTP Trigger node activates when an external system sends an HTTP request to the workflow endpoint. The node parses the incoming request and extracts three data components: the request body, query string parameters, and headers.
Each component is mapped to a separate workflow variable, making the data accessible to downstream nodes. This enables workflows to process data from external APIs, webhooks, or automated systems.
Unlike the User Prompt node which responds to chatbot messages, the HTTP Trigger node responds to programmatic HTTP requests. This makes it suitable for system-to-system integrations and automated workflow invocations.
Configuration
This node has no configuration parameters. It automatically extracts and maps HTTP request components to workflow variables.
Output
| Property | Description |
|---|---|
| Body | The HTTP request body content |
| QueryString | URL query parameters as key-value pairs |
| Headers | HTTP request headers as key-value pairs |
Each output is stored as a separate workflow variable accessible to downstream nodes.
Execution Lifecycle
| Phase | Behavior |
|---|---|
| Pre-execution | Awaits incoming HTTP request |
| Execution | Parses request, extracts Body, QueryString, and Headers |
| Post-execution | Maps extracted data to workflow variables, passes control downstream |
The node transitions from Not Run to Completed immediately upon receiving a valid HTTP request.
Usage Example
Webhook integration workflow:
HTTP Trigger → Data Transformation → Large Language Model → HTTP Response
External API processing workflow:
HTTP Trigger → Validation → Vector Search → Response Output
The request data flows from the trigger through processing stages, enabling automated document processing or API-driven AI responses.
Limitations
- Single entry point: One HTTP Trigger node per workflow
- No authentication handling: Authentication must be managed at the API gateway level
- Synchronous execution: Request waits for workflow completion
- No configuration: Request parsing behavior cannot be customized
Best Practices
- Use HTTP Trigger for system-to-system integrations and webhook receivers
- Validate incoming request data in downstream nodes before processing
- Combine with HTTP Response nodes to return structured responses to callers
- Use User Prompt node instead for chatbot-driven workflows
Related Nodes
- User Prompt - Entry point for chatbot-triggered workflows
- HTTP Response - Return HTTP responses to callers
- Data Transformation - Process and reshape incoming request data
- IF Conditional - Route workflow based on request content